home *** CD-ROM | disk | FTP | other *** search
- $Id: README,v 1.5 1996/01/24 19:26:30 chuck Exp $
-
- ======================================================================
- ATTENTION: vi users set your tabstop to 3 to make this file (and all
- other files) look nice on your screen
- ======================================================================
-
- Q. What is xinetd ?
- A. xinetd is a replacement for inetd, the internet services daemon.
-
-
- Q: I am not a system administrator; what do I care about an inetd replacement ?
- A: xinetd is not just an inetd replacement. Anybody can use it to start servers
- that don't require privileged ports because xinetd does not require that the
- services in its configuration file be listed in /etc/services.
-
-
- Q. Is it compatible with inetd ?
- A. No, its configuration file has a different format than inetd's one
- and it understands different signals. However the signal-to-action
- assignment can be changed and a program has been included to convert
- inetd.conf to xinetd.conf.
-
-
- Q. Why should I use it ?
- A. Because it is a lot better (IMHO) than inetd. Here are the reasons:
-
- 1) It can do access control on all services based on:
- a. address of remote host
- b. time of access
-
- 2) Access control works on all services, whether multi-threaded or
- single-threaded and for both the TCP and UDP protocols.
- All UDP packets can be checked as well as all TCP connections.
-
- 3) It provides hard reconfiguration:
- a. kills servers for services that are no longer in the
- configuration file
- b. kills servers that no longer meet the access control criteria
-
- 4) It can prevent denial-of-access attacks by
- a. placing limits on the number of servers for each service
- (avoids process table overflows)
- b. placing an upper bound on the number of processes it will fork
- c. placing limits on the size of log files it creates
-
- 5) Extensive logging abilities:
- a. for every server started it can log:
- i) the time when the server was started
- ii) the remote host address
- iii) who was the remote user (if the other end runs a
- RFC-931/RFC-1413 server)
- iv) how long the server was running
- (i, ii and iii can be logged for failed attempts too).
- b. for some services, if the access control fails, it can
- log information about the attempted access (for example,
- it can log the user name and command for the rsh service)
-
- 6) No limit on number of server arguments
-
- Q. Where can I find the latest-and-greatest version ?
- A. The xinetd source can be obtained via anonymous FTP from
- gatekeeper.dec.com, in
- pub/usenet/comp.sources.unix/volume26/xinetd-2.1.1
- pub/usenet/comp.sources.unix/volume27/xinetd-2.1.1
- pub/usenet/comp.sources.unix/volume29/xinetd-2.1.1
- You will need the contents of *all* of the above directories
- (the directories in volumes 27 and 29 contain patches).
-
- The xinetd source is also available from ftp.irisa.fr
- in the directory "pub/mirrors/xinetd".
- The BSDI version may be found at ftp.bsdi.com
- in the directory "contrib/networking".
- The Linux version may be found at sunsite.unc.edu
- in the directory "pub/Linux/system/Network/admin".
- The newest Linux and BSDI (and also FreeBSD) versions may be found at
- ftp.telebase.com in the directory "pub/security".
-
- Q. Whom should I thank/blame for this program ?
- A. Any comments about xinetd should be sent to panos@cs.colorado.edu
- Any comments about xinetd for Linux, BSDI, FreeBSD, or NetBSD should be
- sent to chuck@telebase.com (Chuck Murcko)
-
-